-
Notifications
You must be signed in to change notification settings - Fork 549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PROJ: New version 9.4.0 #8746
PROJ: New version 9.4.0 #8746
Conversation
Looks like you might need to update the |
Hmm since this changes the DLL name from Now that it is out, I guess General needs to be updated to block PROJ_jll 901.400? Or better to just yank it? |
Is it actually incompatible? Would changing the library name on Windows to |
I think it is only the library name on Windows that is the issue I think. The PROJ_SOVERSION is the same so the ABI should otherwise be the same. |
That's also how the release notes read. Should we then rename the Windows libraries (and add respective comments) instead of blocking or yanking the package? |
I'd be fine with that if others agree. It seems like the smoothest upgrade path. I tried locally renaming the DLL in the artifact, and
Note that GDAL_jll has a PROJ_jll dependency, but also via libgeotiff_jll. It is libgeotiff_jll that gives the errors: yeesian/ArchGDAL.jl#427 Of course it could be confusing that PROJ 9.4 has a https://github.com/OSGeo/PROJ/blob/9.4.0/cmake/ProjVersion.cmake#L40-L46 |
Actually the |
I propose we yank these two broken/breaking releases; JuliaRegistries/General#107721 Regarding the libproj DLL name, I also created an upstream issue: OSGeo/PROJ#4151 |
Unfortunately that does not work on Windows because the dll name in embedded in the dll itself. |
* PROJ: New version 9.4.0 * PROJ: Use newer GCC version * PROJ: Correct case of cmake variable
No description provided.